Slices for applications based on multiple active sim profiles

ABSTRACT

User circuitry within a wireless User Equipment (“UE”) that may utilize multiple subscriber identity module (“SIM”) profiles activates two or more SIM profiles to be active simultaneously. The user circuitry transfers service requests for wireless data services using the SIM profiles to network circuitry. The wireless data services may have different slice service types over different operating frequency bands of different target cells. The network circuitry wirelessly exchanges data with wireless access nodes associated with the target cells over the operating frequency bands to establish packet data unit sessions comprising the slice service types using the respective SIM profiles such that multiple packet data unit sessions are active using multiple SIM profiles simultaneously. Various applications may be mapped to the appropriate SIM profile and packet data unit session based on the respective provisioned slice characteristics matching the respective application requirements.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services includemachine-control, Internet-access, media-streaming, andsocial-networking. Exemplary wireless user devices comprise phones,computers, vehicles, robots, and sensors. The wireless communicationnetworks have wireless access nodes (e.g., base stations such as eNodeB, gNode B) which exchange wireless signals with the wireless userdevices over radio frequency bands. The wireless signals use wirelessnetwork protocols like Fifth Generation New Radio (5GNR), MillimeterWave (MMW), Long Term Evolution (LTE), Institute of Electrical andElectronic Engineers (IEEE) 802.11 (WIFI), and Low-Power Wide AreaNetwork (LP-WAN). The wireless access nodes exchange network signalingand user data with network elements that are often clustered togetherinto wireless network cores. The wireless access nodes are connected tothe wireless network cores over backhaul data links.

Each wireless access node serves one or more cells that are eachoperating at a selected radio frequency band (i.e., operating frequencyband (“OFB”)). The wireless user devices request access/authorization tothe wireless network based on an active Subscriber Identity Module(“SIM”) profile and its associated allowances on the network based onthe subscriber's carrier, selected package and features, paymenthistory, and so forth. The wireless devices, after authentication,request sessions for communicating with external data networks throughthe wireless access nodes via a cell based on the user application thatis to use the session for communication to external data networks.Certain radio frequency bands offer different advantages anddisadvantages including latency, noise, connection throughput, spectrumefficiency, and the like. The applications using the session may havevarying requirements associated with the radio frequency band such as,for example, low latency, high connection throughput, and the like.Network slicing provides a flexible logical network architecture.Slicing service types include, for example, enhanced Mobile Broadband(eMBB), Ultra Reliable Low Latency Communications (URLLC), and massiveMachine Type Communications (mMTC). Each of the slice service typesoperate best on various OFBs. For example, eMBB is best suited to highfrequency bands, where mMTC is best suited to low frequency bands.However, a wireless user device can only be connected to a single cellon a single OFB at a time based on the active SIM. Accordingly, allallocated slices for the wireless user device operate over the same OFB,which may not provide the best service for the given slice and thecorresponding application requirements.

Technical Overview

User circuitry within a wireless User Equipment (“UE”) that may utilizemultiple subscriber identity module (“SIM”) profiles activates two ormore SIM profiles to be active simultaneously. The user circuitrytransfers service requests for wireless data services using the SIMprofiles to network circuitry. The wireless data services may havedifferent slice service types over different operating frequency bandsof different target cells. The network circuitry wirelessly exchangesdata with wireless access nodes associated with the target cells overthe operating frequency bands to establish packet data unit sessionscomprising the slice service types using the respective SIM profilessuch that multiple packet data unit sessions are active using multipleSIM profiles simultaneously. Various applications may be mapped to theappropriate SIM profile and packet data unit session based on therespective provisioned slice characteristics matching the respectiveapplication requirements.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network that serves awireless User Equipment (UE) that has multiple active SIM profiles.

FIG. 2 a wireless communication network that serves a wireless UserEquipment (UE) that has multiple active SIM profiles that may be subjectto handovers.

FIG. 3 illustrates the operation of the wireless communication networkand the wireless UE to activate and utilize multiple SIM profiles on thewireless UE.

FIG. 4 illustrates a swim diagram of communication on the wirelesscommunication network to activate and utilize multiple SIM profiles onthe wireless UE.

FIG. 5 illustrates a Fifth Generation (5G) communication network thatserves a 5G User Equipment (UE) that activates and utilizes multiple SIMprofiles.

FIG. 6 illustrates the 5G UE that activates and utilizes multiple SIMprofiles.

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 that serveswireless User Equipment (UE) 101. Wireless communication network 100comprises wireless UE 101, wireless access nodes 111 and 112, andnetwork core 120, which includes wireless network slices 121-123. UE 101comprises user circuitry (CKTRY) 102 and network circuitry 103. Usercircuitry 102 comprises user applications (APPS) like augmented-reality,vehicle-control, atmospheric sensing, or some other user service. Usercircuitry 102 further comprises Subscriber Identity Module (“SIM”)profiles (SIM PROFILES). The SIM profiles may include one or morephysical standalone SIMs stored on a Universal Integrated Circuit Card(“UICC”) and/or one or more embedded SIM (“eSIM”) stored on an embeddedUICC (“eUICC”). Wireless network slices 121-123 may comprise UltraReliable Low Latency Communication (URLLC) slices, enhanced MobileBroadband (eMBB) slices, massive Machine Type Communication (mMTC)slices, default slices, backup slices, and/or some other type of networkslices. The number of UEs, wireless access nodes, and wireless networkslices that are depicted on FIG. 1 has been restricted for clarity, andwireless communication network 100 may comprise many more UEs, nodes,and slices.

Various examples of network operation and configuration are describedherein. In some examples, upon startup of UE 101, user circuitry 102activates more than one SIM PROFILE. In some embodiments, networkcircuitry 103 exchanges data with wireless network core 120 via wirelessaccess node 111 to authenticate UE 101 on the network using one or moreSIM PROFILES. For example, the network circuitry 103 may authenticatethe UE 101 with a first SIM PROFILE (e.g., SIM profile 1) and the usercircuitry 102 may share the authentication with the other SIM PROFILES(e.g., SIM profile 2). As another example, the network circuitry 103 mayauthenticate the UE 101 with each active SIM PROFILE. During thewireless network exchange, wireless network core 120 may approve one ormore network slices 121-123 for each active SIM PROFILE, and each SIMPROFILE may utilize a preferred network slice 121-123 based on apreferred slice service type for the SIM PROFILE. The network circuitry103 may then select a cell with a preferred operating frequency band foreach SIM PROFILE connection such that the SIM PROFILE utilizes a cellwith an operating frequency band that corresponds to the preferred sliceservice type for the SIM PROFILE. For example, a SIM PROFILE that has apreferred slice service type of eMBB may use a very high frequency bandwhere a SIM PROFILE that has a preferred slice service type of mMTC mayuse a lower frequency band. While a single antenna is depicted in UE101, multiple antennas may be used to communicate with different cellsof the wireless access nodes 111 and 112 simultaneously. The UE 101 isthen camped on a cell with a given frequency for each SIM PROFILE, suchthat the UE 101 is camped on multiple cells at multiple frequencies,each using a different slice for each SIM PROFILE. In some examples,user circuitry 102 executes a user application and identifies anassociation between the user application and the SIM PROFILE or theslice service type. For example, the user application may includeinformation that maps the user application to a SIM PROFILE or to aslice service type. The user circuitry 102 transfers a service requestfor a corresponding wireless data service having the slice service typeto network circuitry 103. Network circuitry 103 may wirelessly exchangesignaling with wireless access node 111 over a frequency band (F1) toselect wireless network slice 121 having the slice service typeidentified based on the user application. Wireless access node 111 andwireless network slice 121 exchange the data to establish a packet dataunit session for the user application using the network slice 121.

As shown in FIG. 1 , after performing the startup of the UE 101discussed above, the wireless UE 101 is camped on cell 1 using OFB 1 ofwireless access node 111 using SIM profile 1 and slice 121. The wirelessUE 101 is also camped on cell 2 using OFB 2 of wireless access node 111using SIM profile 2 and slice 122. Any user applications that arelaunched on UE 101 may then be mapped to the appropriate communicationconnection with the appropriate slice and OFB based on mappings withinthe user application to the SIM PROFILE or the slice type, for example.

Advantageously, UE 101 efficiently obtains the appropriate wirelessnetwork slices 121-123 over the appropriate or preferred OFB usingmultiple SIM profiles simultaneously such that applications are able tobe mapped to a connection to obtain the best fit to service requirementsof the application which may limit service impact from frequent handoveror service impact from using a frequency and slice that is notappropriate for the application because it is the only one available. Inprevious systems, a UE has only one connection on an OFB that allapplications must use. Using multiple active SIM PROFILES allows the UE101 to map applications to the most appropriate OFB and slice for theapplication when the application starts. Further, handovers of the UE101 may be performed on a per-connection basis, such that a first SIMprofile may not be handed over to a different cell at the same time as asecond SIM profile, which has different service needs and quality ofservice at any given time because of different OFBs.

UE 101 and wireless access nodes 111 and 112 wirelessly communicate overwireless links using Radio Access Technologies (RATs) like FifthGeneration New Radio (5GNR), Long Term Evolution (LTE), Institute ofElectrical and Electronic Engineers (IEEE) 802.11 (WIFI), Low-Power WideArea Network (LP-WAN), and/or some other wireless protocol. The RATs useelectromagnetic frequencies in the low-band, mid-band, high-band, orsome other portion of the electromagnetic spectrum. Wireless accessnodes 111 and 112 and wireless network slices 121-123 communicate overbackhaul links that use metallic links, glass fibers, radio channels, orsome other communication media. The backhaul links use IEEE 802.3(Ethernet), Time Division Multiplex (TDM), Data Over Cable SystemInterface Specification (DOCSIS), Internet Protocol (IP), General PacketRadio Service Transfer Protocol (GTP), 5GNR, LTE, WIFI, virtualswitching, inter-processor communication, bus interfaces, and/or someother data communication protocols. While FIG. 1 depicts two wirelessaccess nodes 111 and 112, any number of wireless access nodes 111 and112 may be included in wireless communication network 100. The depictionof two wireless access nodes is limited for clarity. Similarly, threenetwork slices 121-123 are depicted in FIG. 1 for clarity, and anynumber of wireless network slices 121-123 may be included in wirelesscommunication network 100.

UE 101 comprises a vehicle, sensor, robot, computer, phone, or someother data appliance with wireless communication circuitry includingnetwork circuitry 103. Wireless access nodes 111 and 112 are depicted astowers but wireless access nodes 111 and 112 may use other mountingstructures or no mounting structure at all. Wireless access nodes 111and 112 may comprise gNodeBs, eNodeBs, NB-IoT access nodes, LP-WAN basestations, wireless relays, and/or some other wireless networktransceivers. UE 101 and wireless access nodes 111 and 112 compriseantennas, amplifiers, filters, modulation, and analog/digitalinterfaces. UE 101, wireless access nodes 111 and 112, and wirelessnetwork slices 121-123 comprise microprocessors, software, memories,transceivers, bus circuitry, and the like. The microprocessors compriseDigital Signal Processors (DSP), Central Processing Units (CPU),Graphical Processing Units (GPU), Application-Specific IntegratedCircuits (ASIC), and/or the like. The memories comprise Random AccessMemory (RAM), flash circuitry, disk drives, and/or the like. Thememories store software like operating systems, user applications, radioapplications, and network functions. The microprocessors retrieve thesoftware from the memories and execute the software to drive theoperation of wireless communication network 100 as described herein. Insome examples, wireless network slices 121-123 comprise User PlaneFunctions (UPFs), Gateways (GWs), and/or other network elements that arehosted by a Network Function Virtualization Infrastructure (NFVI).

FIG. 2 illustrates wireless communication network 100 after a handoverhas occurred. Multiple types of handovers may be possible, and eachconnection may be handed over independently of other connections. Afirst type of handover may be a standard handover of the connection, asshown with the handover of SIM profile 1 communication. A second type ofhandover may be a handover of the user applications using a SIM PROFILEto a second SIM PROFILE connected to a different cell, as shown with thehandover of the applications using SIM profile 2 to SIM profile 3.

A handover may occur, for example, when a quality of service (“QOS”) orother metric for a connection falls below a threshold. For example, whena UE 101 mobility status changes (e.g., UE 101 begins moving), ahandover may be needed. However, differing connections of the UE 101 mayhave differing requirements to handover each of the connections.

The SIM profile 1 is using a connection to cell 1 using OFB 1 onwireless access node 111 and slice 121. One or more user applicationsmay be using the connection, and a handover may be required because theconnection metrics may fall below a threshold. The network circuitry 103may perform a cell reselection. The network circuitry 103 performs thecell reselection by exchanging data with the wireless access node 112that is operating over the OFB 3. Once the network circuitry 103performs the cell reselection, the network circuitry 103 requests thePDU session with the wireless network slice 121. Once the PDU session isestablished, the network circuitry 103 exchanges data with the usercircuitry 102 and with the wireless access node 112 to provide thewireless service for the user applications using the SIM profile 1 onthe wireless UE 101.

SIM profile 2 is using a connection to cell 2 using OFB 2 on wirelessaccess node 111 and slice 122. One or more user applications may beusing the connection, and a handover may be required because theconnection metrics may fall below a threshold. Another SIM profile 3 mayhave a connection with wireless access node 112 on cell 4 and OFB 4using slice 122. The user applications using SIM profile 2 may be handedover to SIM profile 3 to use the connection established for SIM profile3. PDU sessions may be established for the user applications using slice122 and SIM profile 3 on cell 4 using OFB 4 on wireless access node 112.

FIG. 3 illustrates the operation 300 of wireless communication network100 and wireless UE 101 to utilize multiple SIM profiles simultaneously.The operation is exemplary and may vary in other examples. In UE 101,user circuitry 102 activates two or more SIM profiles to be activesimultaneously (305). The user circuitry 102 transfers a first servicerequest for a first wireless data service using a first SIM profile tonetwork circuitry 103 (310). The wireless data service requested has afirst slice service type over a first operating frequency band of afirst target cell. The user circuitry 102 transfers a second servicerequest for a second wireless data service using a second SIM profile tonetwork circuitry 103 (315). The second wireless data service requestedhas a second slice service type over a second operating frequency bandof a second target cell. The network circuitry 103 wirelessly exchangesdata with a first wireless access node (111, 112) associated with thefirst target cell over the first operating frequency band to establish afirst packet data unit session including the first slice service typeusing the first SIM profile (320). The network circuitry 103 wirelesslyexchanges data with a second wireless access node (111, 112) associatedwith the second target cell over the second operating frequency band toestablish a second packet data unit session including the second sliceservice type using the second SIM profile (325). The first packet dataunit session remains active using the first SIM profile while the secondpacket data unit session is established and is active.

Additional steps may be included in operation 300. For example, thenetwork circuitry 103 wirelessly exchanges data with the respectivewireless access node (111, 112) over the respective operating frequencyband on the respective target cell for each SIM profile for theassociated user applications. For example, network circuitry 103wirelessly exchanges data with the first wireless access node over thefirst operating frequency band using the first packet data unit sessionand associated slice service type for a first user applicationassociated with the first SIM profile and simultaneously wirelesslyexchanges data with the second wireless access node over the secondoperating frequency band using the second packet data unit session andassociated second slice service type for a second user applicationassociated with the second SIM profile. In some embodiments, the usercircuitry 102 launches the first application and maps the firstapplication to use the first packet data unit session based on anassociation between the first application and the first slice servicetype and launches the second application and maps the second applicationto use the second packet data unit session based on an associationbetween the second application and the second slice service type. Insome embodiments, the user circuitry 102 launches the first applicationand maps the first application to use the first packet data unit sessionbased on an association between the first application and the firstoperating frequency band and launches the second application and mapsthe second application to use the second packet data unit session basedon an association between the second application and the secondoperating frequency band. In some embodiments, the user circuitry 102launches the first application and maps the first application to use thefirst packet data unit session based on an association between the firstapplication and the first SIM profile and launches the secondapplication and maps the second application to use the second packetdata unit session based on an association between the second applicationand the second SIM profile. In some embodiments, the user circuitry 102transfers a third service request for a third wireless data serviceusing a third SIM profile to the network circuitry 103, the thirdwireless data service having the first slice service type over a thirdoperating frequency band of a third target cell. The network circuitry103 wirelessly exchanges data with a third wireless access node (111,112) associated with the third target cell over the third operatingfrequency band to establish a third packet data unit session includingthe first slice service type using the third SIM profile. The usercircuitry 102 hands over the first application from the first SIMprofile to the third SIM profile, and the network circuitry 103wirelessly exchanges data of the first application with the thirdwireless access node. The handover may be in response to data latency,data reliability, or data throughput falling below a target threshold onthe first target cell or in response to a change in the mobility of thewireless UE 101. The network circuitry 103 may complete a cellreselection from the first target cell to a third target cell using thefirst SIM profile while the second packet data unit session using thesecond SIM profile remain on the second target cell. In someembodiments, the first operating frequency band is selected based on thefirst slice service type and the second operating frequency band isselected based on the second slice service type. The first slice servicetype may be a preferred slice service type defined in the first SIMprofile, and the second slice service type may be a preferred sliceservice type defined in the second SIM profile. The slice service typesmay be, for example, eMBB, URLLC, or mMTC.

FIG. 4 illustrates a swim diagram 400 of communication on the wirelesscommunication network to simultaneously use multiple SIM profiles andobtain network slices using the desired slice service types andoperating frequency bands for user applications when camped on multiplecells operating over the operating frequency bands. The operation isexemplary and may vary in other examples. In this example, wirelessnetwork slice 121 comprises the selected slice service type for SIMprofile 1 and wireless network slice 122 comprises the selected sliceservice type for SIM profile 2. In this example, UE 101 activates SIMprofile 1 and SIM profile 2 simultaneously. Subsequently, wireless UE101 executes, for example, an augmented-reality application thatrequires a low-latency service associated with SIM profile 1 and asocial media application that requires a mobile broadband serviceassociated with SIM profile 2. Accordingly, in this example, the sliceservice type for network slice 121 may be URLLC and the slice servicetype for network slice 122 may be eMBB.

The UE 101 is camped on a cell served by wireless access node 111 forSIM profile 1 and on a cell served by wireless access node 112 for SIMprofile 2. The wireless access node 111 periodically wirelesslybroadcasts a System Information Block (“SIB”) containing informationabout the wireless access node 111, and the wireless access node 112periodically wirelessly broadcasts a SIB containing information aboutthe wireless access node 112. The network circuitry 103 may exchangedata from the SIB with the user circuitry 102, and the user circuitry102 may save the information from the SIB in memory.

In UE 101, user circuitry 102 executes the augmented realityapplication. Upon launching an application, the UE 101 initiates theRadio Resource Control (“RRC”) connection setup procedure. Duringprevious wireless communications with the wireless access node 111, theUE 101 may have been provided with allowed network slice information towhich the UE 101 SIM profile 1 has access. A network slice is identifiedby its Single Network Slice Selection Assistance Information(“S-NSSAI”), which is a concatenation of a slice service type (8 bits)and a slice differentiator (24 bits). The slice differentiator isoptional and used to differentiate between network slices having thesame slice service type value. A set of one or more S-NSSAI are anNSSAI. The user circuitry 102 identifies the slice service type, the SIMprofile, or an operating frequency band based on an association with theaugmented reality application. In this example, for instance, the sliceservice type may be URLLC. The user circuitry 102 transmits a servicerequest to the network circuitry 103 requesting wireless data servicehaving the slice service type URLLC. In response, the network circuitry103 identifies wireless access node 111 on which UE 101 is camped usingSIM profile 1. The network circuitry 103 transmits an RRC request thatincludes a requested NSSAI, typically generated from the already knownallowed NSSAI or from previously configured NSSAI, and which includesthe desired URLLC to wireless access node 111. Wireless access node 111transmits the request to the wireless network core 120. The wirelessnetwork core 120 responds with the NSSAI that the wireless UE 101 areallowed to use. In this example, the wireless network core 120 allowsthe requested NSSAI. The wireless access node 111 transmits the allowedNSSAI information to the UE 101 wirelessly. Other wirelesscommunications may be exchanged between UE 101, wireless access node111, and wireless network core 120 that are not included here forclarity.

Upon receipt of the RRC registration acceptance, the network circuitry103 initiates an RRC PDU request to the wireless access node 111 thatincludes the S-NSSAI of network slice 121 that is specific to the sliceservice type identified by the user circuitry for the augmented realityapplication. The request also includes the Data Network Name (“DNN”) andmay include other parameters not depicted here. The wireless access node111 transmits the request to the wireless network core 120 and receivesan acceptance from the wireless network core 120 that initiates the PDU.The wireless access node 111 transmits the acceptance to the networkcircuitry 103. The network circuitry 103 wirelessly exchanges data withthe wireless access node 111 over the selected OFB to provide thewireless service to the augmented reality application using networkslice 121, and the network circuitry 103 exchanges data with usercircuitry 102 to provide and request information for operating theaugmented reality application.

Additionally, in UE 101, user circuitry 102 executes the social mediaapplication. Upon launching an application associated with the SIMprofile 2, the UE 101 initiates the Radio Resource Control (“RRC”)connection setup procedure. During previous wireless communications withthe wireless access node 112, the UE 101 may have been provided withallowed network slice information to which the UE 101 SIM profile 2 hasaccess. The user circuitry 102 identifies the slice service type, theSIM profile, or an operating frequency band based on an association withthe social media application. In this example, for instance, the sliceservice type may be eMBB. The user circuitry 102 transmits a servicerequest to the network circuitry 103 requesting wireless data servicehaving the slice service type eMBB. In response, the network circuitry103 identifies wireless access node 112 on which UE 101 is camped usingSIM profile 2. The network circuitry 103 transmits an RRC request thatincludes a requested NSSAI, typically generated from the already knownallowed NSSAI or from previously configured NSSAI, and which includesthe desired eMBB to wireless access node 112. Wireless access node 112transmits the request to the wireless network core 120. The wirelessnetwork core 120 responds with the NSSAI that the wireless UE 101 areallowed to use. In this example, the wireless network core 120 allowsthe requested NSSAI. The wireless access node 112 transmits the allowedNSSAI information to the UE 101 wirelessly. Other wirelesscommunications may be exchanged between UE 101, wireless access node112, and wireless network core 120 that are not included here forclarity.

Upon receipt of the RRC registration acceptance, the network circuitry103 initiates an RRC PDU request to the wireless access node 112 thatincludes the S-NSSAI of network slice 122 that is specific to the sliceservice type identified by the user circuitry for the social mediaapplication. The request also includes the Data Network Name (“DNN”) andmay include other parameters not depicted here. The wireless access node112 transmits the request to the wireless network core 120 and receivesan acceptance from the wireless network core 120 that initiates the PDU.The wireless access node 112 transmits the acceptance to the networkcircuitry 103. The network circuitry 103 wirelessly exchanges data withthe wireless access node 112 over the selected OFB to provide thewireless service to the social media application using network slice122, and the network circuitry 103 exchanges data with user circuitry102 to provide and request information for operating the social mediaapplication while the augmented reality application continues to executeand the network circuitry 103 wirelessly exchanges data with thewireless access node 111 to provide the wireless service to theaugmented reality application using network slice 121 and the networkcircuitry 103 exchanges data with the user circuitry 102 to provide andrequest information for operating the augmented reality application.

FIG. 5 illustrates Fifth Generation (5G) communication network 500 thatserves 5G User Equipment (UE) 501 that utilizes multiple active SIMprofiles simultaneously. 5G communication network 500 comprises anexample of wireless communication network 100, although network 100 maydiffer. 5G communication network 500 comprises 5G UE 501, 5G RadioAccess Network (RAN) 510, and 5G network core 520. 5G RAN 510 comprisesRadio Units (RUs) 511-518, Distributed Units 531 and 532, andCentralized Unit (CU) 541. 5G network core 520 comprises eMBB User PlaneFunction (UPF) 521, URLLC UPF 522, mMTC UPF 523, Access and MobilityManagement Function (AMF) 524, Network Slice Selection Function (NSSF)525, and Session Management Function (SMF) 526. Other network functionsare typically present but are omitted for clarity. RUs 511 and 512 use afirst frequency band (F1) that is a few thousand megahertz wide. RUs513-515 use a second frequency band (F2) that is several hundredmegahertz wide. RUs 516-518 use a third frequency band (F3) that is afew hundred megahertz wide.

Based on signal strength, UE 501 using SIM profile 1 wirelessly attachesto RU 511 over F1 and exchanges attachment signaling with CU 541 over RU511 and DU 531. UE 501 sends requests for frequency bands F1-F3 and foreMBB, URLLC, and mMTC slices to AMF 524 over RU 511, DU 531, and CU 541.AMF 524 authorizes bands F1-F3 for UE 501 responsive to the UE requestin the RRC exchange described in FIG. 4 . AMF 524 interacts with NSSF525 to authorize UE 501 for the eMBB, URLLC, and mMTC slices responsiveto the request in the RRC exchange described in FIG. 4 . AMF 524indicates authorized F1-F3 bands and authorized eMBB, URLLC, and mMTCslices to UE 501 over CU 541, DU 531, and RU 511.

UE 501 executes an augmented reality application, identifies the URLLCslice service type based on the application based on an association inthe augmented reality application. UE 501 selects the authorized URLLCslice based on the association with the augmented reality application.UE 501 attaches to CU 541 over RU 511 and DU 531. Over RU 511, DU 531,and CU 541, UE 501 instructs SMF 526 to activate the authorized URLLCslice in response to the PDU establishment request as described withrespect to FIG. 4 . In response, SMF 526 selects URLLC bearer QoS andaddressing for UE 501. SMF 526 selects and controls URLLC UPF 522 toserve the URLLC bearer to CU 541 per the QoS and addressing. AMF 524controls CU 541 to serve the URLLC bearer between UE 501 and URLLC UPF522 over F1, RU 511, and DU 531. CU 541 signals DU 531 and RU 511 todeliver the URLLC bearer over F1 per the URLLC QoS and addressing. CU541 signals UE 501 over DU 531 and RU 511 to use the URLLC bearer overF1 for the URLLC slice. UE 501 and URLLC UPF 522 now exchange user dataover F1, RU 511, DU 531, and CU 541.

Based on signal strength, UE 501 using SIM profile 2 wirelessly attachesto RU 513 over F2 and exchanges attachment signaling with CU 541 over RU513 and DU 531. UE 501 sends requests for frequency bands F1-F3 and foreMBB, URLLC, and mMTC slices to AMF 524 over RU 513, DU 531, and CU 541.AMF 524 authorizes bands F1-F3 for UE 501 using SIM profile 2 responsiveto the UE request in the RRC exchange described in FIG. 4 . AMF 524interacts with NSSF 525 to authorize UE 501 for the eMBB, URLLC, andmMTC slices responsive to the request in the RRC exchange described inFIG. 4 . AMF 524 indicates authorized F1-F3 bands and authorized eMBB,URLLC, and mMTC slices to UE 501 over CU 541, DU 531, and RU 513.

UE 501 executes a social media application, identifies the eMBB sliceservice type based on an association in the social media application. UE501 selects the authorized eMBB slice based on the association with thesocial media application. UE 501 attaches to CU 541 over RU 513 and DU531. Over RU 513, DU 531, and CU 541, UE 501 instructs SMF 526 toactivate the authorized eMBB slice in response to the PDU establishmentrequest as described with respect to FIG. 4 . In response, SMF 526selects eMBB bearer QoS and addressing for UE 501. SMF 526 selects andcontrols eMBB UPF 521 to serve the eMBB bearer to CU 541 per the QoS andaddressing. AMF 524 controls CU 541 to serve the eMBB bearer between UE501 and eMBB UPF 521 over F2, RU 513, and DU 531. CU 541 signals DU 531and RU 513 to deliver the eMBB bearer over F2 per the eMBB QoS andaddressing. CU 541 signals UE 501 over DU 531 and RU 513 to use the eMBBbearer over F2 for the eMBB slice. UE 501 and eMBB UPF 521 now exchangeuser data over F2, RU 513, DU 531, and CU 541.

As UE 501 moves about, UE 501 and CU 541 may perform handovers for theURLLC slice over F1 from RU 511 to RU 512 (or another RU or band). Whilethe handover may not be required at the same time, handovers for theeMBB slice over F2 may be performed from RU 513 to RU 514-515. UE 501and CU 541 may perform handovers for the mMTC slices over F3 from RU 516to RUs 517-518 (or another RU or band) if needed. For each SIM profile,the handovers ideally remain on the same OFB as originated as preferred,and/or are handed to a cell operating at the preferred OFB if notavailable when the PDU was established. For example, prior to ahandover, the network circuitry 103 may exchange information with theuser circuitry 102, and user circuitry 102 may identify a preferred OFBfor the network circuitry 103 to measure prior to a handover. If themeasurement reveals a target cell is suitable over the preferred OFB,the handover may be to the target cell.

As UE 501 moves around, the QoS for RU 511 may fall below a threshold.UE 501 measures the F1 signal (e.g., SINR, RSRP or any other appropriatemeasurement), of RU 512 and transfers a cell reselection request to F1on RU 512. CU 541 selects RU 512 based on the best F1 signal. CU 541directs UE 501 using SIM profile 1 to attach to RU 512 over F1 andcontrols RU 512 and DU 531 to serve UE 501 using SIM profile 1 over F1.CU 541 notifies AMF 524 of the cell reselection to F1 and RU 512. UE 501attaches to CU 541 over RU 512 and DU 531. Over RU 512, DU 531, and CU541, UE 501 instructs SMF 526 to activate the authorized URLLC slice inresponse to the PDU establishment request as described with respect toFIG. 4 . In response, SMF 526 selects URLLC bearer QoS and addressingfor UE 501. SMF 526 selects and controls URLLC UPF 522 to serve theURLLC bearer to CU 541 per the QoS and addressing. AMF 524 controls CU541 to serve the URLLC bearer between UE 501 and URLLC UPF 522 over F1,RU 512, and DU 531 using handovers. CU 541 signals DU 531 and RU 512 todeliver the URLLC bearer over F1 per the URLLC QoS and addressing. CU541 signals UE 501 over DU 531 and RU 512 to use the URLLC bearer overF1 and to use handovers for the URLLC slice. UE 501 and URLLC UPF 522now exchange user data over F1, RU 512, DU 531, and CU 541.

FIG. 6 illustrates 5G UE 501 that activates and utilizes multiple SIMprofiles simultaneously. UE 501 comprises an example of UE 101, althoughUE 101 may differ. UE 501 comprises 5GNR radios 601-603 and usercircuitry 604. 5GNR radios 601-603 comprise antennas, amplifiers,filters, modulation, analog-to-digital interfaces, DSP, memory, andtransceivers that are coupled over bus circuitry. User circuitry 604comprises memory, CPU, user interfaces and components, and transceiversthat are coupled over bus circuitry. The memory in user circuitry 604stores an operating system, user applications (USER APPS), the SIMPROFILES, and 5GNR network applications for PHY, MAC, RLC, PDCP, SDAP,and RRC. The antennas in 5GNR radios 601-603 are wirelessly coupled to5G RAN 510 over OFBs F1-F3. Transceivers in 5GNR radios 601-603 arecoupled to a transceiver in user circuitry 604. A transceiver in usercircuitry 604 is typically coupled to the user interfaces and componentslike displays, controllers, and memory. The CPU in user circuitry 604executes the operating system, PHY, MAC, RLC, PDCP, SDAP, and RRC toexchange 5GNR signaling and data with 5G RAN 510 over 5GNR radios601-603.

In 5GNR radios 601-603, the antennas receive wireless signals from 5GRAN 510 that transport downlink 5GNR signaling and data. The antennastransfer corresponding electrical signals through duplexers to theamplifiers. The amplifiers boost the received signals for filters whichattenuate unwanted energy. Demodulators down-convert the amplifiedsignals from their carrier frequency (F1-F3). The analog/digitalinterfaces convert the demodulated analog signals into digital signalsfor the DSPs. The DSPs transfer corresponding 5GNR symbols to usercircuitry 604 over the transceivers. In user circuitry 604, the CPUexecutes the network applications to process the 5GNR symbols andrecover the downlink 5GNR signaling and data. The 5GNR networkapplications receive new uplink signaling and data from the userapplications. The network applications process the uplink usersignaling, the downlink 5GNR signaling to generate new downlink usersignaling, and new uplink 5GNR signaling. The network applicationstransfer the new downlink user signaling and data to the low-latencyuser applications. The 5GNR network applications process the new uplink5GNR signaling and low-latency user data to generate correspondinguplink 5GNR symbols that carry the uplink 5GNR signaling and data. In5GNR radios 601-603, the DSPs process the uplink 5GNR symbols togenerate corresponding digital signals for the analog-to-digitalinterfaces. The analog-to-digital interfaces convert the digital uplinksignals into analog uplink signals for modulation. Modulationup-converts the uplink analog signals to their carrier frequency(F1-F3). The amplifiers boost the modulated uplink signals for thefilters which attenuate unwanted out-of-band energy. The filterstransfer the filtered uplink signals through duplexers to the antennas.The electrical uplink signals drive the antennas to emit correspondingwireless 5GNR signals to 5G RAN 510 that transport the uplink 5GNRsignaling and data.

RRC functions comprise authentication, security, handover control,status reporting, QoS, network broadcasts and pages, and networkselection. SDAP functions comprise QoS marking and flow control. PDCPfunctions comprise security ciphering, header compression anddecompression, sequence numbering and re-sequencing, de-duplication. RLCfunctions comprise ARQ, sequence numbering and resequencing,segmentation and resegmentation. MAC functions comprise buffer status,power control, channel quality, HARQ, user identification, randomaccess, user scheduling, and QoS. PHY functions comprise packetformation/deformation, windowing/de-windowing,guard-insertion/guard-deletion, parsing/de-parsing, controlinsertion/removal, interleaving/de-interleaving, FEC encoding/decoding,channel coding/decoding, channel estimation/equalization, and ratematching/de-matching, scrambling/descrambling, modulationmapping/de-mapping, layer mapping/de-mapping, precoding, REmapping/de-mapping, FFTs/IFFTs, and DFTs/IDFTs.

Based on signal strength detected by radio 601, the RRC in UE 501wirelessly attaches to RU 513 in RAN 510 over OFB F2 and exchangesattachment signaling with CU 541 for SIM profile 3. The RRC in UE 501requests OFBs F1-F3 and eMBB, URLLC, and mMTC slices to AMF 524 innetwork core 520 over 5G RAN 510. AMF 524 indicates authorized F1-F3bands and authorized eMBB, URLLC, and mMTC slices to the RRC in UE 501over 5G RAN 510.

UE 501 executes a video-conferencing application and selects thecorresponding and authorized eMBB slice service type. UE 501 identifiesa preferred OFB F2, slice service type eMBB, and or SIM profile 3 basedon associations in the video-conferencing application. In response toselecting the eMBB slice and identifying F2 as the preferred OFB, UE 501measures the F2 signal (e.g., SINR, RSRP, or any other appropriatemeasurement), of RUs 513-515 and transfers a cell reselection request toF2 based on the measurement being suitable. For example, 5G radio 602and the F2 PHY measure the response of RUs 513-515 in 5G RAN 510. TheRRC transfers a cell addition request for F2 and an F2 report to CU 541.CU 541 selects RU 515 based on the best F2 signal and directs the RRC inUE 501 to attach to RU 515 over F2. UE 501 attaches to RU 515 over F2.The RRC in UE 501 instructs SMF 526 to activate the authorized eMBBslice. CU 541 signals the RRC in UE 501 to use the eMBB bearer over F2.The SDAP in UE 501 and eMBB UPF 521 now exchange eMBB user data overradio 602, F2, RU 515, DU 532, and CU 541 to support thevideo-conferencing application. Simultaneously, UE 501 may execute anaugmented-reality application and the SDAP in UE 501 and URLLC UPF 522may exchange URLLC user data over radio 601, F1, RU 511, DU 531, and CU541 to support the augmented-reality application.

As UE 501 moves about, the RRC in UE 501 and CU 541 may performhandovers for the eMBB slice over F2 from RU 515 to RUs 513 or 514 (oranother RU or band). Handovers ideally remain on the same OFB asoriginated as preferred, and/or are handed to a cell operating at thepreferred OFB if not available when the PDU was established. Forexample, prior to a handover, the network circuitry 103 may exchangeinformation with the user circuitry 102, and user circuitry 102 mayidentify the preferred OFB, slice service type, and/or SIM profile. Theuser circuitry may use this information to provide to the networkcircuitry 103 to measure an appropriate OFB prior to a handover. If themeasurement reveals a target cell is suitable over the preferred OFB,the handover may be to the target cell.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose UE circuitry to usespecific handover types for specific wireless network slices. Thecomputer hardware comprises processing circuitry like CPUs, DSPs, GPUs,transceivers, bus circuitry, and memory. To form these computer hardwarestructures, semiconductors like silicon or germanium are positively andnegatively doped to form transistors. The doping comprises ions likeboron or phosphorus that are embedded within the semiconductor material.The transistors and other electronic structures like capacitors andresistors are arranged and metallically connected within thesemiconductor to form devices like logic circuitry and storageregisters. The logic circuitry and storage registers are arranged toform larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executes physicallyembedded machine-level software that drives the compilation andexecution of the other computer software components which then assertcontrol. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose UE circuitry to usespecific handover types for specific wireless network slices.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless User Equipment(UE) to utilize multiple subscriber identity module (SIM) profiles, themethod comprising: user circuitry activating two or more SIM profiles tobe active simultaneously; the user circuitry transferring a firstservice request for a first wireless data service using a first SIMprofile of the two or more SIM profiles to network circuitry, the firstwireless data service having a first slice service type over a firstoperating frequency band of a first target cell; the user circuitrytransferring a second service request for a second wireless data serviceusing a second SIM profile of the two or more SIM profiles to thenetwork circuitry, the second wireless data service having a secondslice service type over a second operating frequency band of a secondtarget cell wherein the first operating frequency band is selected basedon the first slice service type and the second operating frequency bandis selected based on the second slice service type; the networkcircuitry wirelessly exchanging data with a first wireless access nodeassociated with the first target cell over the first operating frequencyband to establish a first packet data unit session comprising the firstslice service type using the first SIM profile; and the networkcircuitry wirelessly exchanging data with a second wireless access nodeassociated with the second target cell over the second operatingfrequency band to establish a second packet data unit session comprisingthe second slice service type using the second SIM profile while thefirst packet data unit session remains active using the first SIMprofile.
 2. The method of claim 1, further comprising: the usercircuitry launching a first application and mapping the firstapplication to use the first packet data unit session based on anassociation between the first application and the first slice servicetype; the user circuitry launching a second application and mapping thesecond application to use the second packet data unit session based onan association between the second application and the second sliceservice type; and the network circuitry exchanging data of the firstapplication with the first wireless access node and exchanging data ofthe second application with the second wireless access node.
 3. Themethod of claim 1, further comprising: the user circuitry launching afirst application and mapping the first application to use the firstpacket data unit session based on an association between the firstapplication and the first operating frequency band; the user circuitrylaunching a second application and mapping the second application to usethe second packet data unit session based on an association between thesecond application and the second operating frequency band; and thenetwork circuitry exchanging data of the first application with thefirst wireless access node and exchanging data of the second applicationwith the second wireless access node.
 4. The method of claim 1, furthercomprising: the user circuitry launching a first application and mappingthe first application to use the first packet data unit session; theuser circuitry transferring a third service request for a third wirelessdata service using a third SIM profile of the two or more SIM profilesto the network circuitry, the third wireless data service having thefirst slice service type over a third operating frequency band of athird target cell; the network circuitry wirelessly exchanging data witha third wireless access node associated with the third target cell overthe third operating frequency band to establish a third packet data unitsession comprising the first slice service type using the third SIMprofile; the user circuitry handing over the first application from thefirst SIM profile to the third SIM profile; and the network circuitrywirelessly exchanging data of the first application with the thirdwireless access node.
 5. The method of claim 4, wherein the usercircuitry handing over the first application from the first SIM profileto the third SIM profile is in response to at least one of data latency,data reliability, or data throughput falling below a threshold on thefirst target cell.
 6. The method of claim 4, wherein the user circuitryhanding over the first application from the first SIM profile to thethird SIM profile is in response to a change in the mobility of thewireless UE.
 7. The method of claim 1, further comprising: the networkcircuitry completing a cell reselection from the first target cell to athird target cell using the first SIM profile, wherein the second packetdata unit session using the second SIM profile remains on the secondtarget cell.
 8. The method of claim 7, wherein the cell reselection iscompleted in response to at least one of a change in the mobility of thewireless UE, data latency falling below a threshold on the first targetcell, data reliability falling below a threshold on the first targetcell, or data throughput falling below a threshold on the first targetcell.
 9. The method of claim 1, wherein the first operating frequencyband comprises a first bandwidth and the second operating frequencycomprises a second bandwidth.
 10. The method of claim 1, wherein thefirst slice service type comprises one of enhanced Mobile Broadband(eMBB), Ultra Reliable Low Latency Communications (URLLC), or massiveMachine Type Communications (mMTC) and the second slice service typecomprises a different one of eMBB, URLLC, or mMTC.
 11. A wireless UserEquipment (UE) to utilize multiple subscriber identify module (SIM)profiles, the wireless UE comprising: user circuitry configured toactivate two or more SIM profiles to be active simultaneously; the usercircuitry configured to transfer a first service request for a firstwireless data service using a first SIM profile of the two or more SIMprofiles to network circuitry, the first wireless data service having afirst slice service type over a first operating frequency band of afirst target cell; the user circuitry configured to transfer a secondservice request for a second wireless data service using a second SIMprofile of the two or more SIM profiles to the network circuitry, thesecond wireless data service having a second slice service type over asecond operating frequency band of a second target cell wherein thefirst operating frequency band is selected based on the first sliceservice type and the second operating frequency band is selected basedon the second slice service type; the network circuitry configured towirelessly exchange data with a first wireless access node associatedwith the first target cell over the first operating frequency band toestablish a first packet data unit session comprising the first sliceservice type using the first SIM profile; and the network circuitryconfigured to wirelessly exchange data with a second wireless accessnode associated with the second target cell over the second operatingfrequency band to establish a second packet data unit session comprisingthe second slice service type using the second SIM profile while thefirst packet data unit session remains active using the first SIMprofile.
 12. The wireless UE of claim 11, wherein: the user circuitry isconfigured to launch a first application and mapping the firstapplication to use the first packet data unit session based on anassociation between the first application and the first slice servicetype; the user circuitry is configured to launch a second applicationand mapping the second application to use the second packet data unitsession based on an association between the second application and thesecond slice service type; and the network circuitry is configured toexchange data of the first application with the first wireless accessnode and exchanging data of the second application with the secondwireless access node.
 13. The wireless UE of claim 11, wherein: the usercircuitry is configured to launch a first application and mapping thefirst application to use the first packet data unit session based on anassociation between the first application and the first operatingfrequency band; the user circuitry is configured to launch a secondapplication and mapping the second application to use the second packetdata unit session based on an association between the second applicationand the second operating frequency band; and the network circuitry isconfigured to exchange data of the first application with the firstwireless access node and exchanging data of the second application withthe second wireless access node.
 14. The wireless UE of claim 11,wherein: the user circuitry is configured to launch a first applicationand mapping the first application to use the first packet data unitsession; the user circuitry is configured to transfer a third servicerequest for a third wireless data service using a third SIM profile ofthe two or more SIM profiles to the network circuitry, the thirdwireless data service having the first slice service type over a thirdoperating frequency band of a third target cell; the network circuitryis configured to wirelessly exchange data with a third wireless accessnode associated with the third target cell over the third operatingfrequency band to establish a third packet data unit session comprisingthe first slice service type using the third SIM profile; the usercircuitry is configured to hand over the first application from thefirst SIM profile to the third SIM profile; and the network circuitry isconfigured to wirelessly exchange data of the first application with thethird wireless access node.
 15. The wireless UE of claim 14, wherein theuser circuitry handing over the first application from the first SIMprofile to the third SIM profile is in response to at least one of datalatency, data reliability, or data throughput falling below a thresholdon the first target cell.
 16. The wireless UE of claim 14, wherein theuser circuitry handing over the first application from the first SIMprofile to the third SIM profile is in response to a change in themobility of the wireless UE.
 17. The wireless UE of claim 11, wherein:the network circuitry is configured to complete a cell reselection fromthe first target cell to a third target cell using the first SIMprofile, wherein the second packet data unit session using the secondSIM profile remains on the second target cell.
 18. The wireless UE ofclaim 17, wherein the cell reselection is completed in response to atleast one of a change in the mobility of the wireless UE, data latencyfalling below a threshold on the first target cell, data reliabilityfalling below a threshold on the first target cell, or data throughputfalling below a threshold on the first target cell.
 19. The wireless UEof claim 11, wherein the first operating frequency band comprises afirst bandwidth and the second operating frequency band comprises asecond bandwidth.
 20. The wireless UE of claim 11, wherein the firstslice service type comprises one of enhanced Mobile Broadband (eMBB),Ultra Reliable Low Latency Communications (URLLC), or massive MachineType Communications (mMTC) and the second slice service type comprises adifferent one of eMBB, URLLC, or mMTC.